fix: Update mssql extractor to utilize proper case for case sensitive MSSQL databases #2234
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Correct SQL code's table and column case so mssql extractor works with case sensitive instances
Description
Some SQL Server databases are configured as case sensitive. Changes were made for utilizing proper case in
required areas.
Motivation and Context
Extractor will not work on mssql databases that are case sensitive
How Has This Been Tested?
Ran the SQL code on SQL database with case sensitivity, tested the extractor against non-case sensitive and case sensitive
databases. Ran on windows 10 with python 3.12 on local machine.
Documentation
CheckList